-
Notifications
You must be signed in to change notification settings - Fork 817
Blog: Optimizing promql queries #6697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
* `ID` - ID of the block (ULID) | ||
* `meta.json` - Contains the metadata of the block | ||
* `index` - A binary file that contains the index | ||
* `chunks` - Directory containing the chunk segment files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* `chunks` - Directory containing the chunk segment files. | |
* `chunks` - Directory containing the chunk segment files |
Hi @harry671003, could you move docs/blog/optimizing-promql-queries.md under /website/content/en/blog/2025 after rebasing from the master branch? I've set up the blog with #6725. |
478d400
to
d3f03aa
Compare
Signed-off-by: 🌲 Harry 🌊 John 🏔 <[email protected]>
d3f03aa
to
62cb34f
Compare
@CharlieTLe - Thanks for creating the blogs page. I've moved this there too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we exclude this change and only keep website/content/en/blog/2025/optimizing-promql-queries.md?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we exclude this change and only keep website/content/en/blog/2025/optimizing-promql-queries.md?
What this PR does:
There has been some talk about creating a blog in Cortex.
#6471
This is my attempt at writing a blog post on optimizing PromQL queries with the audience being new users or Prometheus and Cortex.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]